-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Add support for custom unnecessary locations on a diagnostic. #39649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
LMK when you'd like a review. thanks! |
I think you should be able to take a look. Was thinking about just encoding the locations into the property bag, but I think this ends up being easier since I get the conversion to |
src/EditorFeatures/Core/Implementation/Diagnostics/DiagnosticsClassificationTaggerProvider.cs
Outdated
Show resolved
Hide resolved
src/EditorFeatures/Core/Implementation/Diagnostics/DiagnosticsClassificationTaggerProvider.cs
Show resolved
Hide resolved
src/EditorFeatures/Core/Implementation/Diagnostics/DiagnosticsClassificationTaggerProvider.cs
Show resolved
Hide resolved
src/EditorFeatures/Core/Implementation/Diagnostics/DiagnosticsClassificationTaggerProvider.cs
Outdated
Show resolved
Hide resolved
mavasani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM. Just have some suggestions around adding more defensive code and adding an example to doc comments. Lets hope we can use the API you added to get rid of the remaining fake fading diagnostics in follow-up PR(s).
389c190 to
09bd524
Compare
db7f64f to
2501c21
Compare
No description provided.